Strike Finance Liquidity Deployment
2026-07-14
Summary
RCADA votes ABSTAIN on Strike Finance Liquidity Deployment.
This is a positive and constructive abstention.
RCADA recognises the strength of the proposal and the importance of what it is trying to achieve. Strike Finance has demonstrated real traction within Cardano DeFi, with significant trading volume, active users, protocol revenue, and liquidity-provider returns. The proposal is also not structured as a conventional grant. It is presented as a 12-month productive Treasury deployment, with Treasury-owned capital converted into USDM, deployed into Strike Finance V2 liquidity infrastructure, and returned to the Cardano Treasury with realized yield at the end of the term.
RCADA is supportive of exploring productive Treasury deployment as a concept. Cardano should be willing to consider responsible ways for Treasury assets to support ecosystem liquidity, strengthen Cardano-native DeFi, retain trading activity on-chain, and potentially generate returns for the Treasury.
However, this proposal also asks the Cardano Treasury to enter a new and higher-risk category of governance action. Unlike a grant, this deployment places Treasury-owned capital into live DeFi liquidity infrastructure. That introduces risk to principal, smart contract and protocol risk, drawdown risk, custody and multisig governance risk, stablecoin exposure, execution risk, and precedent risk.
RCADA abstains rather than voting no because the proposal is thoughtful, innovative, and potentially useful, but we do not yet believe the safeguards and governance framework are mature enough for full support at this scale.
Key Considerations
- This proposal requests a 12-month productive Treasury deployment of 9,000,000 ADA into Strike Finance V2 liquidity infrastructure.
- The proposal is framed as a productive deployment, not grant funding.
- Treasury-owned ADA would be sold for USDM and deployed as stablecoin-denominated liquidity.
- The proposal models approximately 1,350,000 USDM of liquidity at ADA = $0.15.
- Under modeled assumptions, the deployment is expected to generate approximately 900,000 ADA-equivalent in annual yield, though returns are not guaranteed.
- Strike Finance reports significant existing traction, including more than $1.1B in cumulative volume, around 1M trades, more than 3,000 unique traders, and more than $1.16M in protocol revenue.
- Realized yield from the first six months would be returned to the Cardano Treasury at month 6.
- At month 12, 100% of Treasury-owned deployed assets, including remaining principal and realized yield, would be returned to the Cardano Treasury.
- The proposal uses an independent council composed of Rami from Snek, Phil from Surf, and James from Moneta/Monetra as administrator and multisig oversight.
- Strike Finance would not have unilateral custody or control of Treasury assets.
- The proposal includes monthly public transparency reports and third-party assurance reports.
- The proposal discloses key risks, including ADA opportunity-cost risk, USDM stablecoin risk, smart contract risk, yield underperformance, drawdown, custody risk, and operational risk.
- RCADA views the concept positively but believes a 9M ADA deployment into protocol-specific DeFi liquidity requires stronger safeguards and a broader Treasury deployment framework.
What this action does
This Treasury Withdrawal proposal requests 9,000,000 ADA for a 12-month productive liquidity deployment into Strike Finance V2.
The requested ADA would be sold into USDM, Cardano’s fiat-backed stablecoin, and deployed into Strike Finance V2 liquidity infrastructure to support stablecoin-denominated perpetual futures liquidity.
The proposal’s intended objectives are to:
- deepen Cardano-native perpetual futures liquidity;
- improve execution quality on Strike Finance V2;
- increase on-chain trading activity;
- retain derivatives trading activity inside Cardano;
- support USDM liquidity;
- generate yield for the Cardano Treasury;
- test a productive Treasury deployment model.
The proposal states that this is not grant funding. Treasury ownership is intended to remain throughout the deployment. Realized yield from the first six months would be returned to the Treasury at month 6, and 100% of Treasury-owned deployed assets, including remaining principal and realized yield, would be returned at month 12.
The proposal also states that any future Treasury participation would require a new governance proposal.
Analysis Findings
Constitutional / Guardrails Assessment
- ✔ The proposal specifies a clear Treasury ask of 9,000,000 ADA.
- ✔ The proposal identifies the purpose of the withdrawal: a 12-month productive liquidity deployment into Strike Finance V2.
- ✔ The proposal identifies the asset conversion plan: ADA sold into USDM.
- ✔ The proposal identifies the administrator as an independent council.
- ✔ The proposal states that Strike Finance will not have unilateral custody or control of Treasury assets.
- ✔ The proposal states that Treasury-owned principal and realized yield are to be returned after 12 months.
- ✔ The proposal includes a midpoint yield return at month 6.
- ✔ The proposal includes public reporting commitments.
- ✔ The proposal includes independent third-party assurance reports.
- ✔ The proposal discloses major risk categories.
- ✔ The proposal states that any ADA held prior to deployment will be auditable, not delegated to an SPO, and delegated to the predefined abstain voting option.
- ⚠ This is not ordinary grant funding; it places Treasury-owned capital into live DeFi liquidity infrastructure.
- ⚠ The proposal exposes the Treasury to principal risk, stablecoin risk, smart contract risk, drawdown risk, and custody/operational risk.
- ⚠ The completed protocol audit should be public and reviewed before any Treasury capital is deployed.
- ⚠ The proposal may establish precedent for protocol-specific productive Treasury deployments without a broader ecosystem framework.
- ⚠ The multisig and custody model is positive, but signer responsibilities, emergency procedures, replacement processes, dispute handling, and wind-down authority should be more formalised.
Assessment: Conditional / High-Risk Pass
Process & Governance Quality
- ✔ The proposal is more thoughtful than a simple subsidy.
- ✔ The proposal distinguishes itself from grant funding and frames the action as a returnable deployment.
- ✔ The proposal includes an independent council rather than unilateral Strike custody.
- ✔ The proposal includes monthly reporting and third-party assurance.
- ✔ The proposal includes midpoint and final return mechanics.
- ✔ The proposal includes risk disclosures and wind-down triggers.
- ✔ Strike Finance has meaningful existing traction and public usage claims.
- ⚠ The deployment category is novel and requires a higher governance standard.
- ⚠ The proposal would give one protocol a significant liquidity advantage.
- ⚠ A broader Treasury deployment policy would help assess fairness, concentration limits, custody standards, and audit requirements.
- ⚠ Review triggers are helpful but are not the same as automatic capital protection.
- ⚠ The proposal relies on modeled returns, not guaranteed returns.
Assessment: Promising but not yet mature enough for full support at this scale
Impact & Risk Analysis
| Risk | Severity | RCADA interpretation |
|---|---|---|
| Custody / multisig governance risk | High | The independent council model is positive, but 9M ADA depends heavily on named individuals coordinating custody, deployment, reporting, risk response, and return of funds. |
| Smart contract / protocol risk | High | Treasury assets would be exposed to Strike V2 infrastructure. A completed and published audit should be reviewed before deployment. |
| Drawdown / market-making loss risk | High | Liquidity provision can lose money even without fraud or an exploit, especially in volatile or one-sided markets. |
| Precedent / policy risk | Medium-High | This could become the first major example of Treasury assets being deployed into protocol-specific DeFi liquidity. |
| USDM stablecoin risk | Medium | USDM may be credible, but stablecoin exposure still creates redemption, liquidity, issuer, regulatory, and depeg considerations. |
| ADA opportunity-cost risk | Medium | Holding USDM may be useful, but the Treasury is still accepting a deliberate ADA-to-stablecoin allocation decision without a broader framework. |
| Concentration / fairness risk | Medium | A 9M ADA deployment gives Strike Finance a major liquidity advantage over other DeFi protocols. |
| Reporting and assurance risk | Medium | Reports must be timely, detailed, independently verifiable, and sufficient to prevent weak accountability norms. |
| Yield underperformance risk | Medium-Low | Lower yield is not fatal if principal is protected and the pilot produces useful learning, but modeled returns should not be treated as guaranteed. |
| Liquidity / exit risk | Medium-Low | Providing liquidity involves exit risk by nature, but wind-down procedures need to be clear and robust. |
| Execution / market-impact risk | Low-Medium | Conversion execution should be staged, transparent, and reported, but this risk is manageable. |
| Performance-metric gaming risk | Low-Medium | Volume and revenue metrics are useful but should be assessed for sustainable quality, not just headline growth. |
RCADA believes the proposal could produce meaningful ecosystem learning and may help develop a future productive Treasury model. However, the combination of custody, smart contract, drawdown, stablecoin, precedent, and fairness risks makes full support difficult without stronger safeguards and broader policy standards.
Assessment: Promising productive deployment pilot / insufficient safeguards for full support at 9M ADA scale
Ratings (Decision Support Only)
| Dimension | Score (1–5) |
|---|---|
| Constitutional clarity | 4 |
| Governance quality | 3 |
| Execution credibility | 3 |
| Ecosystem value | 4 |
| Risk balance | 2 |
| Overall score | 🟡 64% — Positive ABSTAIN for productive Treasury concept, but safeguards not yet sufficient |
RCADA Rationale
RCADA abstains on the Strike Finance Liquidity Deployment proposal.
This is a positive and constructive abstention.
RCADA recognises the strength of the proposal and the importance of what it is trying to achieve. Strike Finance has demonstrated real traction within Cardano DeFi, with significant trading volume, active users, protocol revenue, and liquidity-provider returns. The proposal is also not structured as a conventional grant. It is presented as a 12-month productive Treasury deployment, with Treasury-owned capital converted into USDM, deployed into Strike Finance V2 liquidity infrastructure, and returned to the Cardano Treasury with realized yield at the end of the term. This is an innovative model and could represent an important step toward making the Cardano Treasury more productive rather than purely distributive.
RCADA is supportive of exploring productive Treasury deployment as a concept. Cardano should be willing to consider responsible ways for Treasury assets to support ecosystem liquidity, strengthen Cardano-native DeFi, retain trading activity on-chain, and potentially generate returns for the Treasury. Strike is a credible candidate for that conversation because it has demonstrated usage, a clear liquidity bottleneck, and a proposal that includes reporting, independent administration, yield return, and a defined 12-month term.
However, this proposal also asks the Cardano Treasury to enter a new and higher-risk category of governance action. Unlike a grant, this deployment places Treasury-owned capital into live DeFi liquidity infrastructure. That introduces risk to principal, smart contract and protocol risk, drawdown risk, custody and multisig governance risk, stablecoin exposure, execution risk, and precedent risk. These risks do not make the proposal bad, but they do raise the standard required for full support.
RCADA’s largest concern is custody and operational governance. The use of an independent multisig council is a positive safeguard, and Strike Finance not having unilateral custody is important. However, a 9,000,000 ADA Treasury deployment depends heavily on named individuals coordinating custody, deployment, reporting, risk response, and return of funds. For this scale of public capital, RCADA would prefer to see stronger and more formalised procedures around signer responsibilities, emergency response, signer replacement, dispute handling, wind-down authority, public account publication, and independent verification.
RCADA is also concerned about smart contract and protocol risk. The proposal states that an official audit is expected and will be published, but for a deployment of this size, RCADA believes the completed audit report should be public, reviewed, and understood before Treasury capital is deployed. This is especially important because the deployment would expose the Treasury not only to ordinary market risk but also to the specific mechanics and security assumptions of Strike V2 liquidity infrastructure.
The drawdown and market-making risks are also material. Even without fraud, a hack, or mismanagement, liquidity provision can lose money. In volatile or one-sided markets, the vault may absorb adverse trader PnL, inventory imbalance, poor execution conditions, or strategy underperformance. The proposal includes review and wind-down triggers, which is positive, but review triggers are not the same as automatic protection. Losses may already have occurred before a review or wind-down process begins.
RCADA does not view the ADA-to-USDM conversion as automatically negative. Holding more stablecoin liquidity may become useful for the Cardano Treasury in future, especially if the community develops a deliberate Treasury liquidity or sub-treasury strategy. However, this proposal effectively asks the community to accept stablecoin exposure and productive deployment risk before such a broader framework has been clearly established. USDM may be a credible and familiar Cardano-native stablecoin, but stablecoin exposure still introduces redemption, liquidity, issuer, regulatory, and depeg considerations that should be explicitly governed.
The precedent question is central. This proposal may become a test case for Treasury assets being deployed into specific DeFi protocols. That could be a valuable evolution for Cardano, but it should not happen casually. RCADA would prefer to see clearer ecosystem-level standards for productive Treasury deployment, including eligibility criteria, concentration limits, custody requirements, audit requirements, reporting standards, stablecoin exposure rules, emergency procedures, and fairness principles for other protocols that may seek similar support.
RCADA also notes the concentration and fairness issue. A 9,000,000 ADA deployment into one protocol would provide a significant liquidity advantage to Strike Finance. That may be justified by Strike’s traction and ecosystem value, but future proposals of this type should ideally be assessed within a broader framework so that Treasury liquidity is not perceived as preferential support for one venue over another.
At the same time, RCADA does not want to dismiss the proposal. The structure is more thoughtful than a simple subsidy. The independent council, monthly reporting, third-party assurance, midpoint yield return, final return of principal and yield, risk disclosures, and requirement for any future participation to come back through governance are all positive elements. RCADA also agrees that even a break-even pilot could produce useful learning for Cardano if principal is protected and reporting is transparent.
For these reasons, RCADA abstains rather than voting no. This abstention is not opposition to Strike Finance, nor is it opposition to productive Treasury deployment. It is a signal that the concept is promising, but the safeguards and governance framework are not yet mature enough for RCADA to give full approval to a 9,000,000 ADA deployment into protocol-specific DeFi liquidity.
RCADA would be more comfortable supporting future proposals of this type if they include a completed and published audit before deployment, stronger custody and multisig operating procedures, clearer automatic drawdown and wind-down rules, independent assurance before and during deployment, public reporting standards, and a broader Treasury deployment framework that can apply fairly across the ecosystem.
RCADA abstains constructively, encouraging continued development of productive Treasury models while asking for stronger risk controls before public Treasury capital is deployed at this scale.